Method and apparatus for reducing network resource transmission size using delta compression

ABSTRACT

A method and computing device for delta compression techniques for reducing network resource transmission size are described. A first version of a network resource is received. The first version of the network resource is stored regardless of a directive that a cached version is not to be used to respond to a future request for that network resource. A first request for the network resource is received. A second request for the network resource is transmitted, to a second computing device. A response including a set differences between the first version of the network resource with a most current version of the network resource is received from the second computing device without receiving the entire network resource. An updated version of the network resource is transmitted to the client device, where the updated version is generated by applying the set of differences to the first version of the network resource.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/002,401, filed Jun. 7, 2018, which is a continuation of Ser. No.15/656,928, filed Jul. 21, 2017 (now U.S. Pat. No. 10,021,206 issuedJul. 10, 2018), which is a continuation of U.S. application Ser. No.14/659,909, filed Mar. 17, 2015 (now U.S. Pat. No. 9,729,657 issued Aug.8, 2017), which is a continuation of U.S. application Ser. No.13/440,658, filed Apr. 5, 2012 (now U.S. Pat. No. 8,984,166 issued Mar.17, 2015), which are hereby incorporated by reference.

TECHNICAL FIELD

Embodiments of the invention relate to the field of networking; and morespecifically, to reducing network resource transmission size using deltacompression.

BACKGROUND ART

Network resources are commonly requested and retrieved using theHypertext Transport Protocol (HTTP). A common approach to improvingperformance is caching network resources closer to the clients (often inseveral different data centers are differently geographically located).For example, content delivery networks (CDNs) are commonly used to cacheresources such as static resources (e.g., resources that changeinfrequently such as images, videos, etc.) closer to clients.

Resources that frequently change (e.g., web sites for news, sports,etc.) may not be cached since the cached version may quickly becomestale. Also, other types of resources may not be cached. As an example,HTTP includes a Cache-Control header field that is used to control thecaching mechanisms along the request/response chain. The Cache-Controlheader field includes a “no-cache” directive that can be set by anorigin server to specify that a cached version of the resource is not tobe used to respond to a request without successful revalidation with theorigin server.

To decrease the size of transmissions of resources, whether from a cacheserver or from an origin server, compression is typically used. Forexample, gzip is a common compression algorithm used to send compressedHTTP responses to clients.

Delta encoding in HTTP has been proposed in RFC 3229, “Delta encoding inHTTP”, January 2002, as a way to reduce the size of resourcetransmission between an origin server and the client. The delta encodingproposal described in RFC 3229 recognizes that if a web resourcechanges, the new version is often similar to the older version. RFC 3229proposes that the difference between the versions be sent to the client(e.g., the browser on a client computing device such as a desktopcomputer, notebook, tablet, smartphone, etc.), and the client appliesthe delta to construct the new version. The approach described in RFC3229 has not been widely adopted because in order to be effective for aresource that changes often, the origin server would have to store manyversions of the website (e.g., an extreme would be a single version foreach single client).

Another proposal for compression is the use of a shared dictionarycompression over HTTP. In the shared dictionary compression, the clientand server agree on a set of predefined elements that will be the sameacross the resources (referred to as cross-payload redundancy). Forexample, the header, footer, and/or other elements of the resource maybe the same. With this proposal, the shared dictionary is downloaded tothe client that contains strings that are likely to appear in subsequentHTTP responses. The server can then substitute those elements with areference to the dictionary when sending the HTTP response and theclient can use its dictionary to reconstruct the resource, therebyreducing the payload of the transmission. This approach has not beenwidely adopted in part because it is administratively difficult tomaintain the dictionaries. For example, if a website is changed (e.g.,it is redesigned), the references in the dictionary will likely need tobe changed and disseminated to the clients. In addition, this approachrequires support on the client devices.

SUMMARY OF THE INVENTION

A near end network optimizer receives, from a client device, a requestfor a network resource. Responsive to determining that a version of thenetwork resource is stored in the near end network optimizer, a requestfor the network resource is transmitted to a far end network optimizeralong with a version identifier that identifies that version. The nearend network optimizer receives, from the far end network optimizer, aresponse that includes a differences file that specifies thedifference(s) between the version of the network resource stored in thenear end network optimizer with a most current version of the networkresource. The response does not include the entire network resource. Thenear end network optimizer applies the specified difference(s) to theversion that it has stored to generate an updated version of the networkresource, and transmits the updated version of the network resource tothe client device.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 illustrates an exemplary system for reducing network resourcetransmission size using delta compression according to one embodiment;

FIG. 2 illustrates the exemplary system of FIG. 1 in more detailaccording to one embodiment;

FIG. 3 illustrates a sequence of exemplary operations performed when anetwork resource is not in the dynamic dictionary of the near endnetwork optimizer according to one embodiment;

FIG. 4 illustrates a sequence of exemplary operations performed when anetwork resource is included in the dynamic dictionary of the near endnetwork optimizer and the same version is not included in the dynamicdictionary of the far end network optimizer according to one embodiment;

FIG. 5 illustrates a sequence of exemplary operations performed when anetwork resource is included in the dynamic dictionary of the near endnetwork optimizer and the same version is included in the dynamicdictionary of the far end network optimizer according to one embodiment;

FIG. 6 is a flow diagram illustrating exemplary operations performed fora delta compression technique for compressing the payload size ofnetwork resources according to one embodiment;

FIG. 7 is a flow diagram illustrating exemplary operations performedwhen the requested resource is not in the dynamic dictionary of the nearend network optimizer and/or the far end network optimizer according toone embodiment;

FIG. 8 illustrates an embodiment where a client network application ofthe client device includes a near end network optimizer according to oneembodiment;

FIG. 9 illustrates an alternative embodiment where a client networkapplication of the client device includes a near end network optimizeraccording to one embodiment; and

FIG. 10 illustrates an exemplary computer system which may be used inembodiments.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth.However, it is understood that embodiments of the invention may bepracticed without these specific details. In other instances, well-knowncircuits, structures and techniques have not been shown in detail inorder not to obscure the understanding of this description. Those ofordinary skill in the art, with the included descriptions, will be ableto implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

In the following description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. It should beunderstood that these terms are not intended as synonyms for each other.“Coupled” is used to indicate that two or more elements, which may ormay not be in direct physical or electrical contact with each other,co-operate or interact with each other. “Connected” is used to indicatethe establishment of communication between two or more elements that arecoupled with each other.

A method and apparatus for reducing network resource transmission sizeusing delta compression is described. The techniques described hereinreduce the network resource transmission size between at least twoendpoints between client devices and origin servers. A first endpoint,which is referred herein as a near end network optimizer, is coupledwith client devices and may be incorporated into a proxy server thatreceives requests (e.g., HTTP requests) from client devices on behalf ofthe origin servers. The first endpoint is also coupled with a secondendpoint, which is referred herein as a far end network optimizer. Thefar end network optimizer may incorporated into a server of a hostingcompany, which itself is coupled to an origin server. The far endnetwork optimizer may alternatively be incorporated into the originserver. In some embodiments, the near end network optimizer is coupledwith the far end network optimizer through a wide area network (WAN)such as the Internet. The near end network optimizer is referred to as anear end since it is closer to the client devices relative to the farend network optimizer, which is closer to the origin server relative tothe client devices.

In one embodiment, when a near end network optimizer transmits a requestfor a network resource to a far end network optimizer, it also sends aversion identifier of the latest version of that network resource thatit has stored (this version is sometimes referred herein as the initialversion). The far end network optimizer determines whether it has accessto that version and if it has, the far end network optimizer retrievesthe most recent version of the network resource (this version issometimes referred herein as the current version and is typicallydifferent than the initial version but it can also be the same as theinitial version), determines the differences between the versions(sometimes referred herein as the delta), and replies to the near endnetwork optimizer with the differences between the versions (and not theentire network resource). The near end network optimizer applies thedifferences to its version of the network resource to generate thelatest version of the resource, and transmits the latest version of theresource to the client device.

Since the difference between versions is transmitted to the near endnetwork optimizer instead of the entire resource, the size of theresponse can be reduced (often substantially). Thus, bandwidth usage isreduced between the near end network optimizer and the far end networkoptimizer. In addition, performance is increased (in particular theamount of time that the resource is delivered to the client) as the nearend network optimizer does not have to wait until the entire resource isreturned.

FIG. 1 illustrates an exemplary system for reducing network resourcetransmission size using delta compression according to one embodiment.FIG. 1 includes the client device 110 that is coupled with the near endnetwork optimizer 120 which is itself coupled with the far end networkoptimizer 140. The client device 110 is a computing device that iscapable of accessing network resources (e.g., laptops, workstations,smartphones, palm tops, mobile phones, tablets, gaming systems, set-topboxes, etc.). The client device 110 includes a client networkapplication (e.g., web browser, FTP client, SSH client, Telnet client,etc.) that is capable of establishing connections for the purpose ofsending requests and receiving network resources. For example, a user ofthe client device 110 requests network resources (e.g., HTML pages,images, word processing documents, PDF files, movie files, music files,or other computer files) through the client network application.Although FIG. 1 illustrates a single client device, it should beunderstood that typically there are many more client devices that arecoupled with the near end network optimizer 120.

In some embodiments, the near end network optimizer 120 is coupled withthe far end network optimizer 140 through a wide area network (WAN) suchas the Internet. In a specific example, the near end network optimizer120 may be part of a proxy server that receives requests (e.g., HTTPrequests) from client devices (including the client device 110) onbehalf of one or more origin servers. By way of a specific example, theproxy server may receive network traffic destined for origin servers(e.g., HTTP requests) as a result of a Domain Name System (DNS) requestfor the domains of the origin servers resolving to the proxy server. Theproxy server may include a cache for returning network resources, aswell as providing other services (e.g., protecting againstInternet-based threats (e.g., proactively stopping botnets, cleaningviruses, trojans, and worms, etc.), performance services (e.g., actingas a node in a CDN and dynamically caching customer's files closer toclients, page acceleration, etc.), and/or other services).

The far end network optimizer 140 may incorporated into a server of ahosting company, which itself is coupled to an origin server (notillustrated for purposes of convenience). The far end network optimizermay alternatively be incorporated into the origin server.

The near end network optimizer 120 includes the dynamic dictionary 124and the far end network optimizer 140 includes the dynamic dictionary144. The dynamic dictionaries are used by the network optimizers tostore version(s) of resources and optionally version identifier(s). Forexample, the dynamic dictionary 124 stores version(s) of resources 126and optionally the version identifiers 128, and the dynamic dictionary144 stores version(s) of resources 146 and optionally the versionidentifiers 148. In one embodiment the dynamic dictionaries 124 and/or144 store only a single version of a resource; in other embodiments thedynamic dictionaries 124 and/or 144 are configured to store multipleversions of a resource. FIG. 1 illustrates the logical structure of thedynamic dictionaries 124 and 144 and the structure may be different indifferent embodiments. In a specific example, the resources fields 126and 146 include a URL portion and a resource portion. When determiningwhether a dynamic dictionary includes a requested resource, the URL ofthe requested resource may be used when accessing the dynamicdictionary.

In another embodiment, the dynamic dictionary 144 may store thedifferences between versions of a resource, in lieu of or in addition tothe actual resource version. The stored differences may be linked orassociated in order to be used to reconstruct the resource versions(e.g., the initial versions), which will be described in greater detaillater herein. For example, the stored differences may be in a chain fromoldest to newest or may be in another format (e.g., a tree structure).Storage space is reduced by storing the differences between versions ofa resource instead of copies of the resource, with a trade off for thetime necessary for reconstruction.

In some embodiments the dynamic dictionaries are built dynamically asrequests for resources are received and retrieved. By way of example,the client device 110 transmits a request 160 for a resource (e.g., anHTTP request), which is received by the request module 122 of the nearend network optimizer 120. The request may be received at the requestmodule 122 as a result of a cache mechanism of the proxy serverdetermining that the requested resource cannot be returned to therequesting client device (e.g., the resource has been set as “no-cache”,the cache has expired, etc.).

The request module 122 accesses the dynamic dictionary 124 to determinewhether it includes a copy of the requested resource. If it does not,then the request module 122 causes a request to be transmitted to thefar end network optimizer 140 for the requested resource. The far endnetwork optimizer 140 retrieves the requested resource (e.g., the farend network optimizer 140 makes a request to the origin server for therequested resource, or if locally available, the far end networkoptimizer 140 accesses the local version), updates its dynamicdictionary 144 to include the latest version of the resource, andreplies to the near end network optimizer 120 with the requestedresource. Updating its dynamic dictionary 144 may include storing aversion identifier, which is a value that identifies a version of anetwork resource, and associating the version identifier with theresource version. By way of a specific example, the version identifiergenerator module 155 may generate the version identifier by hashing thecontents of the resource (e.g., using a suitable hashing algorithm suchas Secure Hash Algorithm (SHA)), with the results being the versionidentifier. As another example, the last-modified header may be used asthe version identifier. As yet another example, a value may be chosenand included in the ETag header field. The response module 150 of thefar end network optimizer 140 causes a response (e.g., an HTTP response)that includes the requested resource to be transmitted to the near endnetwork optimizer 120, which is received by the response module 130. Theresponse may, in some embodiments, include the version identifier. Theresponse may include a no-cache directive.

The response module 130 causes the resource to be stored in the dynamicdictionary 128, along with the version identifier if one was provided inthe response from the far end network optimizer 140. In someembodiments, the response module 130 causes the resource version to bestored in the dynamic dictionary 124 even if it has a no-cache directiveset. Thus, by way of example, a version of a news website, which changesfrequently, is stored in the dynamic dictionary 124 even if the no-cachedirective is set.

In some embodiments, if the version identifier was not included in theresponse from the far end network optimizer 140, the version identifiergenerator module 135 generates a version identifier to store in thedynamic dictionary 124 (e.g., it hashes the resource and stores theresulting value as the version identifier).

After receiving a request for a resource that is the dynamic dictionary124, the near end network optimizer 120 transmits a request 162 for thatresource that includes the version identifier of the last known versionto the far end network optimizer 140. The version identifier may bepreviously stored and associated with the resource, or in someembodiments, the version identifier is generated by the versionidentifier generator module 135 (e.g., the resource is hashed). Therequest may also indicate (e.g., in a header) that it is requesting thedelta between the version identified in the version identifier and thelatest version of the resource.

The request module 142, upon receiving the request 162, accesses itsdynamic dictionary 144 to determine whether it has access to the versionof the resource identified by the version identifier included in therequest 162. In one embodiment, the request module 142 determines hasaccess to the version of the resource if a same copy of that resource isstored in the dynamic dictionary 144. In another embodiment, the requestmodule 142 has access to the identified resource version if that versionof the resource can be reconstructed using the stored differencesbetween versions of a resource. If the request module 142 does not haveaccess to that version, then the far end network optimizer 140 retrievesthe requested resource (e.g., the far end network optimizer 140 makes arequest to the origin server for the requested resource, or if locallyavailable, the far end network optimizer 140 accesses the localversion), updates its dynamic dictionary 144 to include the latestversion of the resource, and replies to the near end network optimizer120 with the requested resource, which may be compressed using asuitable non-delta compression algorithm such as gzip.

If the request module 142 has access to the version (e.g., the dynamicdictionary 144 of the far end network optimizer 140 includes the sameversion of the resource identified by the version identifier included inthe request 162 or that version can be reconstructed using the storeddifferences between versions of that resource), the far end networkoptimizer 140 retrieves the requested resource (e.g., the far endnetwork optimizer 140 makes a request to the origin server for therequested resource, or if locally available, the far end networkoptimizer 140 accesses the local version), updates its dynamicdictionary 144 to include the latest version of the resource, anddetermines the differences between the versions.

For example, the difference determination module 152 determines thedifferences between the versions. A number of algorithms may be used todetermine the differences between the versions, including Xdelta3,VCDIFF (described in RFC 3284, “The VCDIFF Generic Differencing andCompression Data Format”, June 2002), Bentley/McIlroy compression,bsdiff, etc.

In embodiments where the differences between versions of a resource arestored, the difference determination module 152 may traverse thedifferences to reconstruct the initial version (the version identifiedin the request 162) in order to determine the differences between theinitial version and the current version. By doing so, storage space maybe reduced as the versions of the resource may not need to be stored,with a trade off for the time necessary for reconstructing.

The response module 150 causes a response 164 (e.g., an HTTP response)to be transmitted to the near end network optimizer 120, the response164 including the differences between the versions (between the initialversion and the current version). The response 164 does not contain theentire resource. In one embodiment, a header in the response 164indicates that it contains the differences between versions (not theentire resource). The header may also indicate the algorithm used todetermine the differences. In one embodiment, the far end networkoptimizer 140 also transmits the version identifier to the near endnetwork optimizer 120.

In one embodiment, the far end network optimizer 140 also compresses theresponse using a suitable compression algorithm. For example, theresponse may be compressed using gzip. As another example, the responsemay be compressed using zlib compression that is pre-warmed using theversion of the resource identified in the request 162. Pre-warmingallows the compression algorithm to understand more about the data thatis being compressed and therefore typically provides a more accurate andfaster compression. The far end network optimizer 140 may also performpre-warmed compression (e.g., zlib compression) of the HTTP headers ofthe response 164 based on the version of the resource in the dynamicdictionary 144 and identified in the request 162.

The response module 130 of the near end network optimizer 120 receivesthe response 164. The difference application module 132 of the responsemodule 130 applies the differences indicated in the response 164 to theresource version included in the dynamic dictionary 124 to generate thelatest version of the resource. The response module 130 causes aresponse 166 (e.g., an HTTP response) with the requested resource to betransmitted to the client device 110. The response module 130 alsocauses the updated version to be stored in the dynamic dictionary 124,and optionally a version identifier associated with the updated version.

FIG. 2 illustrates the exemplary system of FIG. 1 in more detailaccording to one embodiment. The near end network optimizer 120 receivesa request 210 for a resource A. The resource A may be a HyperText MarkupLanguage (HTML) file, a text document, or any other type of resource.The near end network optimizer 120 determines that is has a version ofthe resource X in its dynamic dictionary 124. As illustrated in FIG. 2,the dynamic dictionary 124 includes the resource X, which is associatedwith the version identifier 7. The near end network optimizer 120 causesa request 220 for resource X to be transmitted to the far end networkoptimizer 140, the request including the version identifier 7.

The far end network optimizer 140 determines that it has access to thesame version (version 7) identified by the version identifier includedin the request 220 for the resource X in its dynamic dictionary 144. Asillustrated in FIG. 2, version 7 of the resource is stored in thedynamic dictionary 144. The far end network optimizer 140 retrieves thelatest version of the resource (referred to in FIG. 2 as version 8)(e.g., the far end network optimizer 140 makes a request to the originserver for the requested resource, or if locally available, the far endnetwork optimizer 140 accesses the local version). The differencedetermination module 152 determines the differences between version 7and version 8 of the resource X. The far end network optimizer 140causes a response 225 to be transmitted to the near end networkoptimizer 120 that identifies the differences between version 7 andversion 8. The differences file that is transmitted to the near endnetwork optimizer 120 is such that the near end network optimizer 120can apply those differences to its latest version of the resource(version 7) to generate the current version (version 8). The far endnetwork optimizer 140 may also include a version identifier. The far endnetwork optimizer 140 updates its dynamic dictionary 144 with the latestversion of resource X (version 8).

Responsive to receiving the differences, the difference applicationmodule 132 applies the differences to the version 7 of the resource X,to generate the version 8 of the resource X. The differences mayindicate to delete content, add content, move content, etc. Aftergenerating the latest version of the resource X, the near end networkoptimizer 120 causes a response 230 to be transmitted to the requestingclient with the version 8 of the resource X. The near end networkoptimizer 120 also updates its dynamic dictionary 124 with the updatedversion of the resource X (version 8).

FIG. 3 illustrates a sequence of exemplary operations performed when anetwork resource is not in the dynamic dictionary of the near endnetwork optimizer according to one embodiment. At operation 310, thenear end network optimizer 120 receives a request for a resource. Next,at operation 315, the near end network optimizer 120 determines that therequested resource is not in its dynamic dictionary 124. As a result, atoperation 320, the near end network optimizer 120 transmits a requestfor the resource 320 to the far end network optimizer 140.

The far end network optimizer 140 receives the request, and retrievesthe most current version of the resource at operation 325. For example,the far end network optimizer 140 transmits a request for the resourceto the origin server, or if locally available, the far end networkoptimizer 140 accesses the local version of the resource.

Next, the far end network optimizer 140 may generate a versionidentifier for the retrieved resource at operation 330. For example, thefar end network optimizer 140 may hash the resource to generate a valuethat is used for the version identifier. In other embodiments, the farend network optimizer 140 does not generate a version identifier. Forexample, the value of the version identifier may be set by the originserver (e.g., the value of the last-modified header, the value of theETag header field). The far end network optimizer 140 stores the versionof the resource in its dynamic dictionary 144 at operation 335, and mayassociate it with the version identifier. In one embodiment, the far endnetwork optimizer 140 may determine the differences between the currentversion (retrieved at operation 325) and the most immediately previousversion (if one exists), store those differences in the dynamicdictionary 144, and may remove older versions of the resource from thedynamic dictionary 144.

The far end network optimizer 140, at operation 340, transmits aresponse to the near end network optimizer 120 that includes therequested resource and optionally includes a version identifier for thatresource. While FIG. 3 illustrates the operation 340 being performedafter the operations 330 and 335, the operations 330 and/or 335 may beperformed after operation 340 in some embodiments.

The near end network optimizer 120 receives the response that includesthe requested resource and transmits a response to the client device 110with the requested resource at operation 345. The near end networkoptimizer 120 stores the requested resource in its dynamic dictionary124 at operation 350. The near end network optimizer 120 may alsogenerate a resource version identifier for the resource at operation355, and may store the resource version identifier at operation 360.

FIG. 4 illustrates a sequence of exemplary operations performed when anetwork resource is included in the dynamic dictionary of the near endnetwork optimizer and the same version is not included in the dynamicdictionary of the far end network optimizer according to one embodiment.

At operation 410, the near end network optimizer 120 receives a requestfor a resource. Next, at operation 415, the near end network optimizer120 determines that the requested resource is in its dynamic dictionary124. As a result, at operation 420, the near end network optimizer 120transmits a request for the resource to the far end network optimizer140, where the request identifies the version identifier of the mostrecent version of the resource that is stored in the dynamic dictionary124 of the near end network optimizer 120.

The far end network optimizer 140 receives the request and determines,in operation 425, that it does not have access to the version of theresource identified in the received request in. For example, its dynamicdictionary 144 does not include the same version of the requestedresource and that version cannot be reconstructed. Since the far endnetwork optimizer 140 does not have access to the version of theresource identified in the received request, it will not be able todetermine the differences between the version in the dynamic dictionary124 of the near end network optimizer 120 and the latest version of theresource. At operation 430, the far end network optimizer retrieves themost current version of the resource. For example, the far end networkoptimizer 140 transmits a request for the resource to the origin server,or if locally available, the far end network optimizer 140 accesses thelocal version of the resource.

Next, the far end network optimizer 140 may generate a versionidentifier for the retrieved resource at operation 435. For example, thefar end network optimizer 140 may hash the resource to generate a valuethat is used for the version identifier. In other embodiments, the farend network optimizer 140 does not generate a version identifier. Forexample, the value of the version identifier may be set by the originserver (e.g., the value of the last-modified header, the value of theETag header field). The far end network optimizer 140 stores the versionof the resource in its dynamic dictionary 144 at operation 340, and mayassociate it with the version identifier. In one embodiment, the far endnetwork optimizer 140 may determine the differences between theretrieved version (retrieved at operation 430) and the most immediatelyprevious version (if one exists), store those differences in the dynamicdictionary 144, and may remove older versions of the resource from thedynamic dictionary 144.

The far end network optimizer 140, at operation 445, transmits aresponse to the near end network optimizer 120 that includes therequested resource and optionally includes a version identifier for thatresource. While FIG. 4 illustrates the operation 445 being performedafter the operations 435 and 440, the operations 435 and/or 440 may beperformed after operation 445 in some embodiments.

The near end network optimizer 120 receives the response that includesthe requested resource and transmits a response to the client device 110with the requested resource at operation 450. The near end networkoptimizer 120 stores the requested resource in its dynamic dictionary124 at operation 455. The near end network optimizer 120 may alsogenerate a resource version identifier for the resource at operation 460and may store the resource version identifier at operation 465.

FIG. 5 illustrates a sequence of exemplary operations performed when anetwork resource is included in the dynamic dictionary of the near endnetwork optimizer and the same version is included in the dynamicdictionary of the far end network optimizer according to one embodiment.

At operation 510, the near end network optimizer 120 receives a requestfor a resource. Next, at operation 515, the near end network optimizer120 determines that the requested resource is in its dynamic dictionary124. As a result, at operation 520, the near end network optimizer 120transmits a request for the resource to the far end network optimizer140, where the request identifies the version identifier of the mostrecent version of the resource that is stored in the dynamic dictionary124 of the near end network optimizer 120.

The far end network optimizer 140 receives the request and determines,in operation 525, that it has access to the version of the resourceidentified in the request of operation 520. For example, the dynamicdictionary 144 includes the same version or that version can bereconstructed using stored version differences. This version of theresource may or may not be the most current version of the resource.Therefore, at operation 530 the far end network optimizer retrieves themost current version of the resource. For example, the far end networkoptimizer 140 transmits a request for the resource to the origin server,or if locally available, the far end network optimizer 140 accesses thelocal version of the resource.

The far end network optimizer 140 determines the differences between theversions of the resource at operation 535. For example, the Xdelta3,VDDIFF, Bentley/Mcllroy compression, bsdiff, or other algorithm that canbe used to determine the differences between the versions of theresource, is used to determine the differences. In a situation where theversion identified in the request of operation 520 (the initial version)is not stored but a chain or tree of differences is, the far end networkoptimizer 140 may traverse the chain or tree of differences toreconstruct the initial version and use that reconstructed version whendetermining the differences between the initial version and the currentversion.

Next, the far end network optimizer 140 may generate a versionidentifier for the retrieved resource at operation 540. For example, thefar end network optimizer 140 may hash the resource to generate a valuethat is used for the version identifier. In other embodiments, the farend network optimizer 140 does not generate a version identifier. Forexample, the value of the version identifier may be set by the originserver (e.g., the value of the last-modified header, the value of theETag header field). The far end network optimizer 140 stores the versionof the resource in its dynamic dictionary 144 at operation 545, and mayassociate it with the version identifier. In one embodiment, the far endnetwork optimizer 140 may determine the differences between the currentversion (retrieved at operation 530) and the most immediately previousversion, store those differences in the dynamic dictionary 144, and mayremove the older versions of the resource from the dynamic dictionary144.

The far end network optimizer 140, at operation 550, transmits aresponse to the near end network optimizer 120 that includes thedifferences between the versions and does not include the completenetwork resource. The response may also include a version identifierassociated with the network resource (that is to identify the version ofthe resource once updated by the near end network optimizer 120). Theresponse may also indicate the algorithm used to generate thedifferences. In one embodiment, if there is not a difference betweenversions of the resource, the far end network optimizer 140 transmits aNULL difference or other message to the near end network optimizer 120that indicates that there are no differences. While FIG. 5 illustratesthe operation 550 being performed after the operations 540 and 545, theoperations 540 and/or 545 may be performed after operation 550 in someembodiments.

The near end network optimizer 120 receives the response, and appliesthe differences to its last known version to generate a current versionof the network resource at operation 555. At operation 560, the near endnetwork optimizer 120 transmits a response to the client device 110 withthe requested resource (the updated resource). The near end networkoptimizer 120 stores the updated resource in its dynamic dictionary 124at operation 565. The near end network optimizer 120 may also generate aresource version identifier for the resource at operation 560 (e.g., ifone was not included in the response 550) and may store the resourceversion identifier at operation 575.

FIG. 6 is a flow diagram illustrating exemplary operations performed fora delta compression technique for compressing the payload size ofnetwork resources according to one embodiment. The operations of thisand other flow diagrams will be described with reference to theexemplary embodiments of FIG. 1. However, it should be understood thatthe operations of the flow diagrams can be performed by embodiments ofthe invention other than those discussed with reference to FIG. 1, andthe embodiments of the invention discussed with reference to FIG. 1 canperform operations different than those discussed with reference to theflow diagrams.

At operation 610, the near end network optimizer 120 receives a requestfor a network resource. By way of example, the request is an HTTPrequest sent from the client device 110 and the resource is identifiedat a Uniform Resource Locator (URL) included in the request. Flow thenmoves to operation 615 where the near end network optimizer 120determines whether the resource is included in the dynamic dictionary124. For example, the request module 122 accesses the dynamic dictionary124 to determine whether the URL for the requested resource is includedand whether there is a corresponding version of the resource. If thereis not, then flow moves to operation 710, which will be described withreference to FIG. 7. If there is a version of the resource in thedynamic dictionary of the near end network optimizer 124, then flowmoves to operation 635.

At operation 635, the near end network optimizer 120 transmits a requestfor the resource to the far end network optimizer 124. The requestincludes a version identifier for the requested resource. In oneembodiment, the version identifier that is included in the request isthe version identifier that is associated with the latest version of theresource that is included in the dynamic dictionary 124. By way of aspecific example, the request may be an HTTP request, and the requestmay also indicate (e.g., in a header) that it is for the delta betweenthe version identified through the included version identifier and thelatest version of the resource. Flow then moves to operation 640.

At operation 640, the far end network optimizer 140 receives the requestand determines whether it has access to the identified version of therequested resource. In one embodiment, the far end network optimizer 140has access to the version of the resource if a same copy of thatresource is stored in the dynamic dictionary 144. In another embodiment,the request module 142 has access to the identified resource version ifthat version of the resource can be reconstructed using the storeddifferences between versions of a resource. For example, the requestmodule 142 searches for the URL of the requested resource in the dynamicdictionary 144. If found, the far end network optimizer 140 compares theversion identifier included in the request with the versionidentifier(s) stored for the resource (if version identifier(s) arestored locally) or stored for the version differences. In embodimentswhere the version identifier(s) are not stored, a version identifier maybe generated by the version identifier generation module 155 andcompared with the version identifier included in the request. If theversion is not accessible, then flow moves to operation 715, which willbe described with reference to FIG. 7. However, if the identifiedversion of the resource is accessible, then flow moves to operation 645.

At operation 645, the far end network optimizer 140 retrieves the mostcurrent version of the requested resource. In some implementations thefar end network optimizer 140 is located in a different geographicallocation than the origin server, where the resource originally residesor is created (the far end network optimizer 140 may be part of the sameLocal Area Network (LAN) as the origin server, or may be located acrossa WAN). In these implementations, the far end network optimizer 140transmits a request towards the origin server (e.g., an HTTP request)requesting the resource (with an expectation that the origin server willreply with the most current version of the resource). In otherimplementations, the far end network optimizer 140 is part of a systemthat has local access to the network resources (e.g., it is implementedin conjunction with the origin server, it is being provided withresources as they are being updated/created by the origin server, etc.).In these implementations, the far end network optimizer 140 accesses thelatest version through local methods. Flow moves from operation 645 tooperation 650.

At operation 650, the far end network optimizer 140 determines thedifference between the versions. For example, the differencedetermination module 152 applies an algorithm such as Xdelta3, VCDIFF,Bentley/Mcllroy compression, bsdiff, or other algorithm suitable fordetermining the differences between versions of files, to determine thedifferences (if any) between the versions. In a situation where theversion identified in the request of operation 635 (the initial version)is not stored but a chain or tree of differences is, the far end networkoptimizer 140 may traverse the chain or tree of differences toreconstruct the initial version and use that reconstructed version whendetermining the differences between the initial version and the currentversion.

Flow then moves to operation 655 where the far end network optimizer 140transmits the difference to the near end network optimizer 120 (and notthe complete resource). For example, the response module 150 formats aresponse (e.g., an HTTP response) that includes a file containing thedifferences between the versions. If there is not any difference, thenthe response includes a NULL difference or otherwise indicates that theversion stored in the dynamic dictionary 124 of the near end networkoptimizer is the most current version. The response may also include aheader that indicates that it contains the differences between versions,and not the entire resource. Also, the response may indicate thealgorithm used to determine the differences. In one embodiment, theresponse is also compressed using gzip or other suitable compressiontechniques. For example, the in some embodiments the far end networkoptimizer 140 performs pre-warmed compression (e.g., zlib compression)of the response and/or the HTTP headers of the response (based on theversion of the resource identified in the request from the near endnetwork optimizer).

The response may also include a version identifier associated with thenetwork resource that is to identify the version of the resource onceupdated by the near end network optimizer 140. The version identifiermay be generated by the far end network optimizer 140 (e.g., a hash ofthe resource version). As another example, the version identifier may beset by the origin server (e.g., the value of the last-modified header,the value in an ETag header field, a hash of the resource, etc.). Flowthen moves to operation 660, where the far end network optimizer 140stores the resource in its dynamic dictionary 144 and optionallyassociates it with the version identifier. In one embodiment, the farend network optimizer 140 may determine the differences between thecurrent version (retrieved at operation 645) and the most immediatelyprevious version, store those differences in the dynamic dictionary 144,and may remove the older versions of the resource from the dynamicdictionary 144. Flow moves from operation 660 to operation 665.

At operation 665, the near end network optimizer 120 applies thedifferences specified in the differences file received from the far endnetwork optimizer 140 to the version of the network resource in itsdynamic dictionary 124 to generate an updated version of the networkresource. For example, the difference file may specify to add content,delete content, move content, etc.

Flow then moves to operation 670 where the near end network optimizer120 transmits the latest version (the updated version of the requestedresource) to the requesting device (e.g., the client device 110). Flowthen moves to operation 675 where the near end network optimizer storesthe latest version in its dynamic dictionary 124 and optionally stores aversion identifier for that version in its dynamic dictionary 124 (whichit may generate, depending on whether the response from the far endnetwork optimizer included the version identifier).

FIG. 7 is a flow diagram illustrating exemplary operations performedwhen the requested resource is not in the dynamic dictionary of the nearend network optimizer and/or the far end network optimizer according toone embodiment. When the requested resource is not in the dynamicdictionary 124 of the near end network optimizer 120, the near endnetwork optimizer 120 transmits a request (e.g., an HTTP request) forthe requested resource to the far end network optimizer 140 at operation710. Flow then moves to operation 715 and the far end network optimizer140 retrieves the latest version of the resource as previouslydescribed. Next, at operation 720, the far end network optimizer 140transmits the requested resource to the near end network optimizer 120,the response optionally including a version identifier of the requestedresource. Flow then moves to operation 725 where the far end networkoptimizer 140 stores the resource in its dynamic dictionary 144 (orupdates its dynamic dictionary) and optionally stores a versionidentifier for that version of the resource. In one embodiment, the farend network optimizer 140 may determine the differences between thecurrent version and the most immediately previous version (if oneexists), store those differences in the dynamic dictionary 144, and mayremove older versions of the resource from the dynamic dictionary 144.

Flow then moves to operation 730, where the near end network optimizer120 transmits the resource to the requesting device. Next, flow moves tooperation 735 where the near end network optimizer 120 stores theresource in its dynamic dictionary 124 and optionally stores a versionidentifier for that version of the resource.

Since the difference between versions is transmitted to the near endnetwork optimizer instead of the entire resource, the size of theresponse can be reduced (often substantially). Thus, bandwidth usage isreduced between the near end network optimizer and the far end networkoptimizer. In addition, performance is increased (in particular theamount of time that the resource is delivered to the client) as the nearend network optimizer does not have to wait until the entire resource isreturned.

In addition, the technique described herein can be used for resourcesthat have been designated as being un-cacheable. As an example, originservers may include a “no-cache” directive in the Cache-Control headerfield of an HTTP response that indicates that a cached version of theresource is not to be used to respond to a request without successfulrevalidation with the origin server. Previously when the no-cachedirective was used, proxy servers checked with the origin server todetermine whether the resource has been updated and if it has, the proxyserver returned with the entire resource, even if there was a minimalchange. However, with the techniques described herein, the near endnetwork optimizer makes a request for the differences (if any) betweenits version and the most recent version and if there is a difference,the far end network optimizer returns the differences and not the entireresource. Also, at least some of the techniques described herein do nothave to be supported by the clients. Thus, in some embodiments, clientsoftware (e.g., client network applications) does not have to be updatedto support the techniques described herein. In addition, unlike thedelta encoding proposal in RFC 3229 which requires coordination betweenthe client devices and the origin servers and would require the originservers to store many versions of the resources (e.g., potentially up toone version for each different client), the techniques described in someembodiments herein allow the far end network optimizer to store only asingle version of each resource. In other embodiments described herein,the differences between versions of a resource are stored in lieu of theactual versions, which reduces the amount of storage space required.

While embodiments have been described with respect to the near endnetwork optimizer being incorporated in a device that is coupled to aclient computing device (e.g., a proxy server), in other embodiments,similar functionality described herein with reference to the near endnetwork optimizer may be incorporated into the client computing device

For example, FIG. 8 illustrates an embodiment where the client networkapplication 815 of the client device 810 includes the near end networkoptimizer 820 that performs similar operations as the near end networkoptimizers previously described herein. For example, the near endnetwork optimizer 820 includes the dynamic dictionary 822, which issimilar to the dynamic dictionary 124 and stores version(s) of resourcesand optionally version identifier(s). The near end network optimizer 820also includes the difference application module 824, which operates in asimilar way as the difference application module 132.

The proxy server 830 includes the far end network optimizer 840, whichoperates in a similar way as the far end network optimizer 140. Forexample, the far end network optimizer 840 includes the dynamicdictionary 842, which is similar to the dynamic dictionary 144 andstores version(s) of resources and optionally version identifier(s). Thefar end network optimizer 840 also includes the difference determinationmodule 844, which operates in a similar way as the differencedetermination module 152.

The client device 810 transmits requests for network resources of theorigin server 850 to the proxy server 830 and receives responses fromthe proxy server 830. In one embodiment, requests (e.g., HTTP requests)are received at the proxy server 830 as a result of a DNS request forthe domain of the origin server 850 resolving to the proxy server 830.In some embodiments, the authoritative name server of the domain of theorigin server is changed and/or individual DNS records are changed topoint to the proxy server (or point to other domain(s) that point to aproxy server of the service). For example, owners and/or operators ofthe domain of the origin server 850 may change their DNS using a CNAMErecord that points to the proxy server 830. While FIG. 8 illustrates asingle proxy server 830, in some embodiments the service has multipleproxy servers that are geographically distributed. For example, in someembodiments, there are multiple point of presences (POPs). A POP is acollection of networking equipment (e.g., authoritative name servers andproxy servers) that are geographically distributed to decrease thedistance between requesting client devices and content. Theauthoritative name servers have the same anycast IP address and theproxy servers have the same anycast IP address. As a result, when a DNSrequest is made, the network transmits the DNS request to the closestauthoritative name server. That authoritative name server then respondswith a proxy server within that POP. Accordingly, a visitor will bebound to that proxy server until the next DNS resolution for therequested domain (according to the TTL (time to live) value as providedby the authoritative name server). In some embodiments, instead of usingan anycast mechanism, embodiments use a geographical load balancer toroute traffic to the nearest POP.

The near end network optimizer 820 dynamically builds the dynamicdictionary 822 in a similar way as previously described herein,according to one embodiment, and is capable of receiving the differencesof network resources and applying those differences to previously storedfiles.

For example, upon determining to transmit a request for a networkresource that is stored in the dynamic dictionary 822 (e.g., as a resultof the network resource being set as “no-cache”, the cached version ofthe network resource in the cache of the client network application 815being expired, etc.), the client network application 815 transmits arequest 860 for the resource, along with the version identifier of thelast known version of that resource to the proxy server 830.

The far end network optimizer 840 receives the request and determineswhether it has access to the identified version of the network resource.Assuming that it does, the far end network optimizer 840 retrieves themost current version of the resource. As illustrated in FIG. 8, theproxy server 830 transmits the request 865 to the origin server 850 forthe requested resource in order to receive the most current version ofthe resource. The proxy server 830 receives the response 870, whichincludes the requested resource.

The difference determination module 844 receives the requested resourceand determines the differences between the versions of the resource aspreviously described. The far end network optimizer 840 causes theresponse 875 to be transmitted to the client network application 815that identifies the differences between the versions. The response 875does not include the entire network resource. The response 875 may alsoinclude a version identifier in some embodiments. The far end networkoptimizer 840 updates its dynamic dictionary 842 with the most currentversion of the resource and may store the differences in the dynamicdictionary 842 and remove old versions of the resource.

Responsive to receiving the differences, the difference applicationmodule 824 applies the differences to its previous version to generatethe most current version of the resource. The most current version maythen be displayed by the client network application 815. The near endnetwork optimizer 820 also updates its dynamic dictionary 822 with theupdated version of the resource.

FIG. 9 illustrates another embodiment where the client networkapplication 915 of the client device 910 includes the near end networkoptimizer 920 that performs similar operations as the near end networkoptimizers previously described herein. For example, the near endnetwork optimizer 920 includes the dynamic dictionary 922, which issimilar to the dynamic dictionary 124 and stores version(s) of resourcesand optionally version identifier(s). The near end network optimizer 920also includes the difference application module 924, which operates in asimilar way as the difference application module 132.

Unlike FIG. 8, FIG. 9 illustrates a proxy server 930 that includesfunctionality of a far end network optimizer (with respect to the clientdevice 910) and of a near end network optimizer (with respect to thehosting provider server 935). The proxy server 930 includes the dynamicdictionary 942, which is similar to the dynamic dictionary 144 andstores version(s) of resources and optionally version identifier(s).

The client device 910 transmits requests for network resources of theorigin server 950 to the proxy server 930 and receives responses fromthe proxy server 930. In one embodiment, requests (e.g., HTTP requests)are received at the proxy server 930 as a result of a DNS request forthe domain of the origin server 950 resolving to the proxy server 930 ina similar was as described with reference to FIG. 8. For example, upondetermining to transmit a request for a network resource that is storedin the dynamic dictionary 922 (e.g., as a result of the network resourcebeing set as “no-cache”, the cached version of the network resource inthe cache of the client network application 915 being expired, etc.),the client network application 915 transmits a request 960 for theresource, along with the version identifier of the last known version ofthat resource to the proxy server 930.

The network optimizer 940 receives the request and determines whether ithas access to the identified version of the network resource. Assumingthat it does, the network optimizer 940 retrieves the most currentversion of the resource. As illustrated in FIG. 9, the proxy server 930transmits the request 965 to the hosting provider server 935, along witha version identifier of the resource. In one embodiment, the versionidentifier included in the request 965 is the same version identifier asincluded in the request 960. In other embodiments, the versionidentifier included in the request 965 is the version identifier of themost recent network resource stored in the dynamic dictionary 942, whichmay or may not correspond with the version identifier included in therequest 960.

The far end network optimizer 952 receives the request and determineswhether it has access to the identified version of the network resource(as identified by the version identifier in the request 965). Assumingthat it does, the far end network optimizer 952 retrieves the mostcurrent version of the resource. As illustrated in FIG. 9, the hostingprovider server 935 transmits the request 970 to the origin server 950for the requested resource in order to retrieve the most current versionof the resource. The hosting provider server 935 receives the response975, which includes the requested resource.

The difference determination module 956 of the far end network optimizer952 receives the requested resource and determines the differencesbetween the versions of the resource as previously described. The farend network optimizer 952 causes the response 980 to be transmitted tothe proxy server 930 that identifies the differences between theversions. The response 980 does not include the entire network resource.The response 980 may also include a version identifier in someembodiments. The far end network optimizer 952 updates its dynamicdictionary 956 with the most current version of the resource and maystore the differences in the dynamic dictionary 956 and remove oldversions of the resource.

Responsive to receiving the differences, the difference applicationmodule 946 applies the difference to its previous version (identified inthe request 965) to generate the most current version of the resource.The difference determination module 944 may also determine thedifference between the most current version of the resource, and theversion identified in the request 960 if the version identified in therequest 960 is different than that of the version identified in therequest 965. The network optimizer 940 causes the response 985 to betransmitted to the client network application 915 that identifies thedifferences between the latest version of the resource and the versionidentified in the request 960. The response 985 may also include aversion identifier in some embodiments. The network optimizer 940updates its dynamic dictionary 942 with the most current version of theresource and may store the differences in the dynamic dictionary 942 andremove old versions of the resource.

Responsive to receiving the differences, the difference applicationmodule 924 applies the differences to its previous version to generatethe most current version of the resource. The most current version maythen be displayed by the client network application 915. The near endnetwork optimizer 920 also updates its dynamic dictionary 922 with theupdated version of the resource.

As illustrated in FIG. 10, the computer system 1000, which is a form ofa data processing system, includes the bus(es) 1050 which is coupledwith the processing system 1020, power supply 1025, memory 1030, and thenonvolatile memory 1040 (e.g., a hard drive, flash memory, Phase-ChangeMemory (PCM), etc.). The bus(es) 1050 may be connected to each otherthrough various bridges, controllers, and/or adapters as is well knownin the art. The processing system 1020 may retrieve instruction(s) fromthe memory 1030 and/or the nonvolatile memory 1040, and execute theinstructions to perform operations described herein. The bus 1050interconnects the above components together and also interconnects thosecomponents to the display controller & display device 1070, Input/Outputdevices 1080 (e.g., NIC (Network Interface Card), a cursor control(e.g., mouse, touchscreen, touchpad, etc.), a keyboard, etc.), and theoptional wireless transceiver(s) 1090 (e.g., Bluetooth, WiFi, Infrared,etc.). In one embodiment, the client devices 110, the server includingthe near end network optimizer 120, the server including the far endnetwork optimizer 140, and/or origin servers, can take the form of thecomputer system 1000.

The techniques shown in the figures can be implemented using code anddata stored and executed on one or more computing devices (e.g., clientdevices, servers, etc.). Such computing devices store and communicate(internally and/or with other computing devices over a network) code anddata using machine-readable media, such as machine-readable storagemedia (e.g., magnetic disks; optical disks; random access memory; readonly memory; flash memory devices; phase-change memory) andmachine-readable communication media (e.g., electrical, optical,acoustical or other form of propagated signals—such as carrier waves,infrared signals, digital signals, etc.). In addition, such computingdevices typically include a set of one or more processors coupled to oneor more other components, such as one or more storage devices, userinput/output devices (e.g., a keyboard, a touchscreen, and/or adisplay), and network connections. The coupling of the set of processorsand other components is typically through one or more busses and bridges(also termed as bus controllers). The storage device and signalscarrying the network traffic respectively represent one or moremachine-readable storage media and machine-readable communication media.Thus, the storage device of a given computing device typically storescode and/or data for execution on the set of one or more processors ofthat computing device. Of course, one or more parts of an embodiment ofthe invention may be implemented using different combinations ofsoftware, firmware, and/or hardware.

While embodiments described herein refer to a single near end networkoptimizer coupled with a single far end network optimizer, embodimentsare not so limited. For example, in some embodiments, multiple near endnetwork optimizers are coupled with a single far end network optimizer.In such embodiments, the far end network optimizer may use the samedynamic dictionary for all of the near end network optimizers in someimplementations, and in other implementations may use a separate dynamicdictionary for each separate near end network optimizer.

In some embodiments there may be multiple pairs of near end networkoptimizers and far end network optimizers between a client computingdevice and the origin server. For example, in such embodiments, a deviceimplementing a far end network optimizer may also be acting as a nearend network optimizer for another far end network optimizer.

While the flow diagrams in the figures show a particular order ofoperations performed by certain embodiments of the invention, it shouldbe understood that such order is exemplary (e.g., alternativeembodiments may perform the operations in a different order, combinecertain operations, overlap certain operations, etc.).

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, can be practiced with modificationand alteration within the spirit and scope of the appended claims. Thedescription is thus to be regarded as illustrative instead of limiting.

What is claimed is:
 1. A method, in a network optimizer of a proxyserver, of supporting a delta compression technique for reducing networkresource transmission size, the method comprising: receiving a firstversion of a network resource, wherein the first version of the networkresource is included in a HyperText Transfer Protocol (HTTP) response;storing, in the proxy server, the first version of the network resourceregardless of a directive associated with the network resource that acached version of the network resource is not to be used to respond to afuture HTTP request for that network resource without successfulrevalidation with an origin server; receiving, from a client device, afirst HTTP request for the network resource; transmitting, to a networkoptimizer of a computing device, a second HTTP request for the networkresource; receiving, from the computing device, a first HTTP responseincluding a set of one or more differences between the first version ofthe network resource stored in the proxy server with a most currentversion of the network resource without receiving the entire networkresource, wherein the first HTTP response further specifies how to applythe set of differences; and transmitting in a second HTTP response, tothe client device, an updated version of the network resource, whereinthe updated version is generated by applying the set of differences tothe first version of the network resource stored in the proxy server,and wherein applying the set of differences includes at least one ofadding content, deleting content, and moving content to the firstversion of the network resource to obtain the updated version of thenetwork resource.
 2. The method of claim 1, further comprising: storinga first version identifier identifying the first version of the networkresource.
 3. The method of claim 2, wherein the second HTTP requestincludes the first version identifier of the first version of thenetwork resource.
 4. The method of claim 3, wherein the second HTTPrequest for the network resource includes an indication that the secondHTTP request is for a difference between the first version of thenetwork resource and the most current version of the network resource.5. The method of claim 1, wherein the first HTTP response furtherincludes an indication that the first HTTP response contains the set ofdifferences between versions and not the entire network resource.
 6. Themethod of claim 1, wherein the first HTTP response further includes anindication of which algorithm was used to determine the set ofdifferences.
 7. The method of claim 1, further comprising: storing theupdated version of the network resource in the proxy server as a secondversion of the network resource.
 8. The method of claim 7, furthercomprising: following the storing of the updated version of the networkresource, removing the first version of the network resource.
 9. Themethod of claim 1, wherein the set of differences is an empty set andthe updated version of the network resource is the first version of thenetwork resource.
 10. A non-transitory machine-readable storage mediumthat provides instructions that, when executed by a processor of a proxyserver including a network optimizer for supporting a delta compressiontechnique for reducing network resource transmission size, cause saidprocessor to perform operations comprising: receiving a first version ofa network resource, wherein the first version of the network resource isincluded in a HyperText Transfer Protocol (HTTP) response; storing, inthe proxy server, the first version of the network resource regardlessof a directive associated with the network resource that a cachedversion of the network resource is not to be used to respond to a futureHTTP request for that network resource without successful revalidationwith an origin server; receiving, from a client device, a first HTTPrequest for the network resource; transmitting, to a network optimizerof a computing device, a second HTTP request for the network resource;receiving, from the computing device, a first HTTP response including aset of one or more differences between the first version of the networkresource stored in the proxy server with a most current version of thenetwork resource without receiving the entire network resource, whereinthe first HTTP response further specifies how to apply the set ofdifferences; and transmitting in a second HTTP response, to the clientdevice, an updated version of the network resource, wherein the updatedversion is generated by applying the set of differences to the firstversion of the network resource stored in the proxy server, and whereinapplying the set of differences includes at least one of adding content,deleting content, and moving content to the first version of the networkresource to obtain the updated version of the network resource.
 11. Thenon-transitory machine-readable storage medium of claim 10, furthercomprising: storing a first version identifier of the first version ofthe network resource.
 12. The non-transitory machine-readable storagemedium of claim 11, wherein the second HTTP request includes the firstversion identifier of the first version of the network resource.
 13. Thenon-transitory machine-readable storage medium of claim 12, wherein thesecond HTTP request for the network resource includes an indication thatthe second HTTP request is for a difference between the first version ofthe network resource and the most current version of the networkresource.
 14. The non-transitory machine-readable storage medium ofclaim 10, wherein the first HTTP response further includes an indicationthat the first HTTP response contains the set of differences betweenversions and not the entire network resource.
 15. The non-transitorymachine-readable storage medium of claim 10, wherein the first HTTPresponse further includes an indication of which algorithm was used todetermine the set of differences.
 16. The non-transitorymachine-readable storage medium of claim 10, further comprising: storingthe updated version of the network resource in the proxy server as asecond version of the network resource.
 17. The non-transitorymachine-readable storage medium of claim 16, further comprising:following the storing of the updated version of the network resource,removing the first version of the network resource.
 18. Thenon-transitory machine-readable storage medium of claim 10, wherein theset of differences is an empty set and the updated version of thenetwork resource is the first version of the network resource.